Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1745

reference
464-tree-1
name
1745
tree-preservation-order

undefined

464-tpo-1
uprn
address-text
point
POINT (-1.027750 50.883401)
geometry
MULTIPOLYGON (((-1.027679 50.883393,-1.027682 50.883407,-1.027692 50.883420,-1.027708 50.883430,-1.027727 50.883437,-1.027749 50.883439,-1.027771 50.883437,-1.027791 50.883431,-1.027807 50.883421,-1.027818 50.883408,-1.027821 50.883395,-1.027818 50.883381,-1.027808 50.883368,-1.027793 50.883358,-1.027773 50.883351,-1.027751 50.883349,-1.027729 50.883351,-1.027709 50.883357,-1.027693 50.883367,-1.027683 50.883380,-1.027679 50.883393)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL